Summary

Pressing Ctrl+C while SSHed into a remote host was dropping the SSH connection entirely (Connection to <host> closed), losing unsaved state in remote editors and aborting long-running remote work. The originally-expected behavior — interrupt the remote process, keep the session alive — is now delivered. Three layered changes deliver Windows-Terminal-parity UX: "Ctrl+C interrupts whatever is running, regardless of whether you're local or in a remote session."

Root cause

SessionManager::send_sigint in crates/forgetty-session/src/manager.rs called kill(-pgid, SIGINT) unconditionally for the foreground pgrp. BUG-001 added it as a fallback for raw-mode apps that swallow 0x03 (Node.js, pm2). But when ssh is the foreground process, the kill landed on the local ssh client itself; OpenSSH installs no SIGINT handler in interactive mode, so the default disposition (terminate) killed it before it could forward the byte to the remote.

QA round 1 then revealed a deeper issue: the bare 0x03 byte we wrote didn't match the remote PTY's VINTR setting. Vick's local PTY has intr = ^X (system-wide on his machine — visible in Ghostty too), and ssh's tty_make_modes() forwards local c_cc to the server via pty-req, so the remote PTY inherits VINTR = ^X too. The line discipline only fires SIGINT when the configured VINTR byte arrives — 0x03 was just echoed and discarded. Round-2 main added dynamic VINTR pickup so the byte we write matches whatever the remote line discipline expects.

QA round 2 then surfaced a cosmetic concern: the remote ECHOCTL echo of the VINTR byte (^X for Vick, ^C for default users) rendered in the terminal after every Ctrl+C — visually mismatched with the key pressed. Round-2 follow-up added a 150 ms client-side filter that drops the first caret-form echo pair after Ctrl+C.

How the fix works

Three coordinated landings:

1. Skip kill for signal-forwarders (forgetty-session/src/manager.rs). In send_sigint, before firing kill(-pgid, SIGINT), check the foreground pgrp leader's /proc/<pgid>/comm against a hardcoded allowlist of { ssh, mosh-client, telnet, rsh }. The kill remains for any non-forwarder so BUG-001's interruption of raw-mode swallowers (Node.js, pm2) still works.

2. Dynamic VINTR byte (forgetty-pty/src/process.rs + forgetty-session + forgetty-socket). PtyProcess::vintr() reads c_cc[VINTR] via libc::tcgetattr on the master fd, exposed via SessionManager::intr_byte(id). handle_send_sigint now writes sm.intr_byte(id).unwrap_or(0x03) instead of hardcoded &[0x03]. The byte we write matches whatever the local — and therefore remote, via ssh's pty-modes forwarding — line discipline treats as the interrupt char.

3. ECHOCTL echo suppression (forgetty-gtk/src/terminal.rs). New TerminalState::suppress_intr_echo_until: Option<Instant> field, set to now + 150ms in the Ctrl+C key handler. New module-private helper drop_first_caret_form_echo() scans incoming DaemonOutputMessage::Data chunks for the first ^<letter> printable pair (caret-form ECHOCTL echo of any control char in 0x00..=0x1f or DEL 0x7f) and removes it before feeding to the VT parser. "Consume on first drop" semantics bound the over-filter blast radius to at most one pair per Ctrl+C press.

The fix never reaches into Forgetty's daily-driver PTY state (all QA inside ./launch-dev.sh sandbox). Architectural invariants AD-007 through AD-011 verified preserved in audit passes.

Tests

11 new unit tests, 207 workspace tests pass (was 196 + 11 new):

• forgetty-session — 3 tests covering the allowlist matcher (ssh / mosh-client / telnet / rsh match; node / python3 / bash / zsh / vim / \"\" / sshd / my-ssh-wrapper do not match) and the I/O wrapper's safe-default on a non-existent pid.
• forgetty-pty — 1 test that vintr() returns Some(0x03) on a freshly-spawned PTY (the kernel default; confirms the tcgetattr plumbing works end-to-end).
• forgetty-gtk — 7 tests for drop_first_caret_form_echo: ^X dropped and flag cleared, default ^C dropped, DEL ^? dropped, no-suppression passthrough, expired-deadline passthrough + flag clear, lowercase ^a not dropped, only-first-match semantics.

Toolchain: cargo fmt --check, cargo check --workspace, cargo clippy --workspace -- -D warnings, cargo test --workspace --exclude forgetty-gtk + cargo test -p forgetty-gtk, cargo build --release — all clean. Zero findings across three audit-skill passes (simplify, audit-rust, audit-security). Daemon smoke test (timeout 5 ./target/release/forgetty-daemon --foreground) — clean exit on SIGTERM.

Performance: two cold-path syscalls per Ctrl+C keypress (~3 µs total). ECHOCTL filter is O(chunk) for ≤150 ms after Ctrl+C; zero allocation in the no-match case (returns Cow::Borrowed). Criterion benches (daemon_hotpath) at-noise vs baseline. AD-009 (no polling on PTY hot path) preserved.

Files

crates/forgetty-gtk/src/app.rs         |   1 -    (cargo fmt blank-line collapse, harmless)
crates/forgetty-gtk/src/terminal.rs    | 154 ++   (suppress_intr_echo_until + ECHOCTL filter + 7 unit tests)
crates/forgetty-pty/src/process.rs     |  45 ++   (PtyProcess::vintr() + 1 unit test)
crates/forgetty-session/src/manager.rs | 108 +-   (allowlist matchers + intr_byte + gated kill + 3 unit tests)
crates/forgetty-socket/src/handlers.rs |  17 ++   (handle_send_sigint reads sm.intr_byte instead of hardcoded 0x03)
docs/socket-api.md                     |   9 ++   (send_sigint description updated to document the new behavior)
6 files changed, 320 insertions(+), 14 deletions(-)

Out of scope

• FIX-018 (wheel scroll broken inside SSH, reported in the same Vick message). Different code path (wheel handler vs key handler), no shared root cause — separate task. Tracked in docs/harness/BACKLOG.md.
• The cosmetic shortcuts-window text mismatch at app.rs:6320 ("Copy Selection — Ctrl+C" labels the wrong accel; the actual registered accel is <Control><Shift>c). Pre-existing doc drift, no functional impact.

Test plan checklist

• cargo fmt --all --check
• cargo check --workspace
• cargo clippy --workspace -- -D warnings
• cargo test --workspace --exclude forgetty-gtk (196 → 207 with the 11 new tests)
• cargo test -p forgetty-gtk (the new echo-filter tests)
• cargo build --release
• T-1 in sandbox: SSH + sleep 100 + Ctrl+C → interrupts, session stays open
• T-2 sanity: local sleep 100 + Ctrl+C → still interrupts
• T-11 in sandbox: SSH with VINTR = ^X + Ctrl+C → interrupts AND no ^X echo printed
• Multi-press Ctrl+C at remote prompt: clean, no ^X echoes

Vick reported: "Fully working and perfect!!"